According to Claude (@claudeai) on Twitter, computer use in Claude Cowork and Claude Code Desktop is now available on Windows, expanding the toolset beyond macOS and browser-based experiences. As reported by the official Claude announcement post, Windows users can now let Claude interact with local files, apps, and development workflows, enabling tasks like repository analysis, build automation, and environment setup directly on the desktop. According to Anthropic’s product communications, this Windows expansion lowers deployment friction for enterprise developers who standardize on Windows, opening opportunities for IT-managed installations, role-based access, and governed AI coding workflows. As reported by the same source link, teams can leverage computer use to accelerate onboarding, code reviews, and repetitive IDE tasks, while centralizing telemetry and permissions for compliance-focused rollouts.

According to Boris Cherny on X (Twitter), Anthropic has introduced a NO_FLICKER mode for Claude Code in the terminal that uses an experimental renderer aimed at eliminating screen redraw flicker and improving readability for AI-assisted coding workflows (source: @bcherny tweet, Apr 1, 2026). As reported by Cherny, most internal users prefer the new renderer over the previous implementation, indicating measurable UX gains for code generation, inline edits, and streaming completions in terminal environments (source: @bcherny). According to the post, the renderer is early and carries tradeoffs, suggesting businesses should pilot it in developer toolchains where stable streaming output and low-latency diffs drive productivity gains for AI pair programming and code review (source: @bcherny).

According to Claude (@claudeai), Auto mode for Claude Code is now available for Enterprise and API users, enabling the assistant to automatically decide on file writes and bash commands with safeguards validating each action before execution. As reported by the official Claude account on X, developers can enable the feature by updating their install and running 'claude --enable-auto-mode', reducing manual approvals while maintaining permission checks. According to the same source, Auto mode targets faster coding workflows, continuous refactoring, and unattended script runs, which can lower context-switching and approval overhead for large engineering teams and CI-like automation. For businesses, this creates opportunities to streamline secure code generation, scripted migrations, and environment setup while preserving governance via pre-run safety checks, according to Claude (@claudeai).

According to Claude on X (@claudeai), Claude Code now supports computer use, enabling the model to open apps, click through UI, and test what it builds directly from the CLI, available in research preview for Pro and Max plans. As reported by Claude on X, this expands Claude’s agentic capabilities from code generation to end-to-end software execution and validation, which can streamline QA workflows, smoke tests, and regression checks for engineering teams. According to the announcement video cited by Claude on X, the feature suggests tighter integration with local or virtualized app environments, creating opportunities for DevOps teams to automate UI testing and post-deploy verification without bespoke test harnesses. As reported by Claude on X, access is limited to Pro and Max subscribers in research preview, indicating early feature gating and potential enterprise pilots focused on developer productivity and autonomous software testing.

According to @bcherny on X, developers can use the Claude Code CLI flag --add-dir (or the /add-dir command) to grant Claude access and permissions to additional repositories when working across multiple codebases, enabling cross-repo context and edits (as reported by the original tweet). According to code.claude.com docs, teams can also set additionalDirectories in settings.json to auto-load extra folders at startup, streamlining multi-repo workflows and reducing manual context switching. As reported by Anthropic’s CLI reference, this approach improves code navigation, search, and refactoring across repos, creating immediate business impact through faster reviews and fewer integration bugs in monorepos and microservices.

According to @bcherny on X, developers can create custom Claude Code agents by defining agent configurations in the .claude/agents directory and invoking them with the claude --agent flag, enabling tailored system prompts and toolchains for coding workflows; as reported by Anthropic’s official docs, sub-agents support specialized behaviors, tool access, and scoped prompts for tasks like refactoring, test generation, and repo triage, offering teams a repeatable way to standardize prompts across projects; according to code.claude.com documentation, organizations can compose multiple sub-agents, assign permissions, and streamline developer operations with reusable agent templates, which can reduce context-switching and improve code review throughput for practical business impact.

According to @bcherny on X, the Claude Code Chrome extension enables the model to verify and iterate on frontend output directly in the browser, improving reliability versus other MCP-based tools (source: X post by Boris Cherny, Mar 30, 2026). As reported by Anthropic’s official docs, the extension integrates with Claude Code to run, preview, and debug web code, creating a closed feedback loop for faster UI iteration (source: Anthropic Claude Code Chrome docs). According to the post, giving Claude a way to validate results—like a live browser—drives better code quality and fewer regressions for web projects, suggesting teams can cut manual review cycles and accelerate shipping (source: X post by Boris Cherny). For businesses, this implies lower frontend QA overhead, faster prototype-to-production timelines, and higher developer throughput in modern web stacks, especially when pairing Claude with browser-based verification to reduce blind spots (sources: X post by Boris Cherny; Anthropic Claude Code docs).

According to Ethan Mollick on X, a resurfaced claim attributed to Anthropic CEO Dario Amodei predicted AI would write 90% of code in 3–6 months and 100% in 12 months; Mollick notes today that while 100% is not reality, Anthropic’s Claude Code now generates a remarkably high share of code, and adoption—not core model capability—is the primary constraint (as reported by Ethan Mollick, citing @kimmonismus). According to the referenced post by @kimmonismus, the prediction video frames rapid displacement potential, but current field experience shows deployment frictions such as security review, repo access, and workflow change management slow enterprise rollout despite strong agentic code generation. As reported by Ethan Mollick, the business opportunity shifts to integration layers: policy-compliant code agents, VCS-integrated review bots, and toolchains that map LLM code to organizational standards, suggesting near-term ROI for vendors that solve permissioning, testing, and observability around Claude Code-driven development.

According to AnthropicAI on X, Anthropic detailed how it designed Claude Code auto mode, a system that replaces user permission prompts with learned classifiers to automatically approve or deny code actions, aiming for safer autonomy in developer workflows. As reported by Anthropic’s Engineering Blog, the team trained and tested approval classifiers on labeled intervention scenarios (e.g., file edits, shell commands, dependency changes) to reduce risky operations while preserving velocity, offering a middle ground between full manual approvals and unrestricted execution. According to Anthropic’s post, offline evaluations and live A/B tests validated that the auto mode cuts prompt fatigue, maintains task completion, and blocks high‑risk actions, creating opportunities for enterprises to scale AI pair‑programming, CI automations, and code refactoring with policy‑aligned guardrails.

According to @bcherny citing @claudeai on X, Anthropic introduced Auto Mode in Claude Code to let the model make file-write and bash-command permission decisions on the user’s behalf, with safeguards validating each action before execution. As reported by the X post, this change removes frequent approval prompts while avoiding fully disabled permissions, enabling faster code generation, refactoring, and shell automation with guardrails. According to the same source, the feature targets developer productivity in tasks like multi-file edits and scripted changes, signaling competitive pressure on agentic coding tools to balance autonomy and safety.

According to Claude (@claudeai) on X, Anthropic introduced Auto Mode in Claude Code that lets the model autonomously approve or deny file writes and bash commands, with safeguards vetting each action before execution (source: Claude on X, Mar 24, 2026). As reported by Claude’s official account, this reduces constant permission prompts while preserving security checks, enabling faster code generation, refactoring, dependency installs, and test runs in IDE-like flows. According to the announcement, teams can expect lower friction in pair-programming scenarios, clearer auditability of actions, and safer continuous iteration compared with fully manual or fully open permissions. For businesses, this feature can improve developer velocity in prototyping and maintenance while maintaining compliance guardrails through pre-execution checks (source: Claude on X).

According to Claude (@claudeai) on Twitter, Anthropic has released Claude Code Auto Mode as a research preview for Team plan users, with Enterprise and API access rolling out in the coming days (source: Claude on Twitter; product page: Anthropic’s Claude Code). According to Anthropic’s product page, developers can enable the feature via the CLI using “claude --enable-auto-mode” and switch to it with Shift+Tab, indicating a workflow-centric design for iterative coding, debugging, and test generation. As reported by Anthropic, staged availability suggests near-term opportunities for software teams to pilot autonomous coding agents, evaluate productivity impacts in code review automation, bug triage, and continuous integration, and prepare governance for API-based integration across secure repos. According to Anthropic’s guidance, early adopters on Team plans can validate use cases like repetitive refactors and scaffolding, while Enterprise buyers should plan access control, audit logging, and policy gates before enabling Auto Mode in production pipelines.

According to Boris Cherny on X, Anthropic has released full computer use capabilities in Claude Cowork and Dispatch, enabling the model to open apps, navigate browsers, and fill spreadsheets on macOS in a research preview (as reported by @claudeai video post). According to Cherny, the Anthropic Labs team previously shipped MCP, Skills, Claude Desktop app, and Claude Code, iterating from early Sonnet 3.6-era prototypes to today’s production-grade features. As reported by @claudeai, this capability turns Claude into an autonomous software operator for desk workflows, suggesting immediate applications in sales ops, finance reconciliation, CRM updates, QA triage, and data entry with measurable productivity gains. According to the X posts by @bcherny and @claudeai, initial rollout is macOS-only, signaling a near-term opportunity for mac-first teams and ISVs to build workflow templates, compliance guardrails, and observability layers around Claude’s computer-use APIs.

According to Boris Cherny on X (Twitter), Anthropic has released Claude Code channels, enabling developers to control Claude Code sessions through Model Context Protocol integrations on Telegram and Discord, allowing direct phone-based messaging to Claude Code; as reported by Thariq (@trq212), this expands Claude Code access beyond the IDE to chat-first workflows and mobile use cases, creating opportunities for faster triage, code review on the go, and lightweight incident response for engineering teams.

According to Ethan Mollick on X, Anthropic released Claude Code channels, enabling users to control Claude Code sessions via Model Context Protocol integrations, starting with Telegram and Discord, and message Claude Code directly from a phone; Mollick cites Thariq (@trq212) noting the Claude team’s rapid adoption of community tools like OpenClaw as evidence that AI-powered coding teams can ship features daily with major strategic implications (source: Ethan Mollick on X referencing Thariq). According to Thariq on X, the Channels feature operationalizes MCP-based control, indicating tighter human-in-the-loop workflows, faster iteration cycles, and mobile-first access for engineering teams (source: Thariq on X). Business impact includes lower time-to-deploy for dev tools, broader developer reach through chat platforms, and potential shifts in software development lifecycles toward continuous AI-assisted delivery (as reported by both Ethan Mollick and Thariq on X).

According to The Rundown AI, Anthropic is introducing the ability to control Claude Code through messaging apps, positioning the feature as a direct response to OpenClaw-style functionalities. As reported by The Rundown AI on X, the update suggests users can trigger code execution, run tasks, and receive outputs within chat interfaces, streamlining developer workflows and enabling lightweight automation. According to The Rundown AI, the move could expand Claude Code’s usage into customer support bots, on-call engineering incident response, and no-code task orchestration, while raising considerations for permissioning, audit logs, and rate limiting. As reported by The Rundown AI, this aligns with a broader trend of agentic AI accessible in everyday communication tools, creating opportunities for SaaS vendors to embed Claude Code into Slack, WhatsApp, and Telegram connectors and monetize usage-based automations.

According to @claudeai, Anthropic is offering a March 2026 bonus usage promotion that applies across all Claude surfaces—including Claude Code—covering Free, Pro, Max, and Team plans, as detailed on the Anthropic Support page (according to Anthropic Support). This promotion expands monthly usage allowances, which can lower overage risk and enable more intensive workflows like longer context chats and code generation for teams and individual developers (as reported by Anthropic Support). For businesses, the cross-plan applicability simplifies procurement and budgeting for AI assistants, while engineering teams can pilot higher-volume use cases—such as embedded agents in IDEs and batch documentation refactors—without immediate plan upgrades (according to Anthropic Support). The official details and eligibility windows are listed in the linked support article and the original tweet by @claudeai.

According to @godofprompt citing @claudeai, Anthropic has made a 1 million token context window generally available for Claude Opus 4.6 and Claude Sonnet 4.6 at standard per-token pricing with no premium multiplier, removing the previous 2x input and 1.5x output surcharge beyond 200K tokens. As reported by @claudeai, a 900K-token request now costs the same per token as a 9K request, enabling entire codebases, long legal contracts, or extended agent sessions to fit in one continuous window. According to @claudeai, Opus 4.6 scores 78.3% on MRCR v2 at 1M tokens, indicating leading long-context recall among frontier models, and Claude Code users on Max, Team, and Enterprise get 1M by default with about 15% fewer compaction events. For enterprises running long-document review, multi-file code analysis, or persistent agent loops, the flat-rate 1M context meaningfully lowers total cost of ownership and reduces retrieval and chunking complexity, according to @godofprompt’s summary of @claudeai’s announcement.

According to @bcherny citing @noahzweben on X, Anthropic’s Claude Code now supports remote control session spawning, allowing users to start a new local coding session on their laptop directly from the Claude mobile app by running 'claude remote-control' (as reported by X posts on Mar 13, 2026: https://x.com/noahzweben/status/2032533699116355819 and https://twitter.com/bcherny/status/2032578639276159438). According to the posts, availability targets Max, Team, and Enterprise tiers on app versions >=2.1.74, requires GitHub on mobile initially, and performance work is underway to reduce session start time. From an AI developer tooling perspective, this enables on-the-go orchestration of Claude-powered coding agents, shorter context-to-commit loops, and smoother handoff between mobile prompts and desktop execution, which can reduce developer friction and increase utilization of paid seats in enterprise environments (as evidenced by the feature notes shared by @noahzweben on X). For businesses, this capability expands mobile-first workflows for incident response, code review, and rapid prototyping while centralizing compute and security policies on the laptop, aligning with enterprise governance needs highlighted in the source posts.

According to @galnagli, RentAHuman—described as a platform where AI agents hire humans for physical tasks—exposed its entire user database, including 187,714 personal emails, which were discoverable within minutes using a few tokens and a single Claude Code command; as reported in Nagli’s X thread on Mar 13, 2026, the workflow demonstrates how LLM-powered code assistants can rapidly chain reconnaissance and misconfiguration exploitation, underscoring urgent needs for secret management, least-privilege database access, and automated leak detection. According to the same thread, the attack path relied on accessible tokens and weak access controls, highlighting immediate business risks for AI agent marketplaces handling PII and the necessity to implement environment variable hygiene, role-based access control, egress filtering, and continuous red-team simulations using agentic scanners.